Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1118

reference
516-tree-1
name
1118
tree-preservation-order

undefined

516-tpo-1
uprn
address-text
point
POINT (-1.021340 50.898751)
geometry
MULTIPOLYGON (((-1.021283 50.898745,-1.021286 50.898756,-1.021294 50.898766,-1.021306 50.898774,-1.021322 50.898779,-1.021339 50.898781,-1.021357 50.898780,-1.021373 50.898775,-1.021386 50.898767,-1.021394 50.898757,-1.021397 50.898746,-1.021394 50.898735,-1.021387 50.898725,-1.021374 50.898716,-1.021358 50.898711,-1.021341 50.898709,-1.021323 50.898711,-1.021307 50.898716,-1.021295 50.898724,-1.021286 50.898734,-1.021283 50.898745)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL